<html>
<head><meta charset="utf-8"><title>json 2.0 · t-compiler/wg-diagnostics · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/147480-t-compiler/wg-diagnostics/index.html">t-compiler/wg-diagnostics</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/147480-t-compiler/wg-diagnostics/topic/json.202.2E0.html">json 2.0</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="161845195"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/147480-t-compiler/wg-diagnostics/topic/json%202.0/near/161845195" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> oli <a href="https://rust-lang.github.io/zulip_archive/stream/147480-t-compiler/wg-diagnostics/topic/json.202.2E0.html#161845195">(Mar 27 2019 at 10:15)</a>:</h4>
<p>I think we should also have a look at other json outputs (e.g. from gcc <a href="https://developers.redhat.com/blog/2019/03/08/usability-improvements-in-gcc-9/" target="_blank" title="https://developers.redhat.com/blog/2019/03/08/usability-improvements-in-gcc-9/">https://developers.redhat.com/blog/2019/03/08/usability-improvements-in-gcc-9/</a>). Ideally we'd be able to come up with a json output that is the same across compilers (maybe with extra fields, but common behaviour should be in the same fields)</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>